Introduction to deploying Calico Network Calico Components:
The Felix:calico agent runs on each node, setting network information for the container: IP, routing Rules, iptable rules, etc.
Etcd:calico Back-End storage
BIRD:BGP Client: Responsible for broadcasting Felix's routing information set on each node to the Calico network (via the BGP Proto
The reference urls:https://github.com/kubernetes/kubernetes/blob/master/docs/getting-started-guides/ ubuntu-calico.mdhttps://github.com/projectcalico/calico-docker/blob/master/docs/kubernetes/ Kubernetesintegration.md I have 3 hosts:10.11.151.97, 10.11.151.100, 10.11.150.101. Unfortunately, there is no Internet access
Reflector(BIRD), used in large-scale deployments, abandons the mesh mode of all nodes interconnection , through one or more BGP Route Reflector to complete the centralized routing distribution. [[email protected] ~]# calicoctl config get ASNumber64512[[email protected] ~]# calicoctl config get NodetonodemeshOn[Email protected] ~]# calicoctl node status650) this.width=650; "src=" Http://s1.51cto.com/wyfs02/M00/8D/1C/wKioL1iIHX6jCNDeAAAavuukWzY685.png "title=" 1.png " alt= "Wkiol1iihx6jcndeaaaa
:2379--advertise-client-urls=http://172.22.0.4:2379 (native IP)Kube-apiserver.json--insecure-bind-address=0.0.0.05. Add nodeKubeadm Join--token b1f4c5.94d2933fea71f20b 172.22.0.4 (master IP)Modifying a configuration file/etc/systemd/system/kubelet.service.d/10-kubeadm.confAt the back of Execstart=/usr/bin/kubelet this adds--hostname-override=172.22.0.6 (node's own IP)Systemctl daemon-reload systemctl Restart Kubelet6. Install calico (at master)Downl
experience for open-source users.
Re-oriented Calicoctl UX model for kubernetes rewriting
There is no doubt that this is Calico's effort and change to better integrate into Kubernetes, and is also good news for users who are increasingly using the k8s while trying to calico the network, so that you can define the C by k8s file as you would define a resource mode
/var/lib/kubelet/*$ service kube-proxy stop rm -fr /var/lib/kube-proxy/*$ service kube-calico stop#停掉master节点的服务$ service kube-calico stop$ service kube-scheduler stop$ service kube-controller-manager stop$ service kube-apiserver stop$ service etcd stop rm -fr /var/lib/etcd/*3.2 Build configuration (all nodes)As with the basic environment, we need to generate all the relevant configuration files for
implementation of Vxlan), are able to complete the overlay network. OvS and flannel and weave subdivision are the different ways to achieve the specific way. OvS is a relatively mature technology, many years of function is also very powerful, but the configuration is complex, for large-scale configuration and project migration, expansion will be a lot of trouble. Flannel, Calico, Weave, Docker1.9 specific differences see I gave above this github blog
. When specifying a plug-in in kubernetes, you need to specify the plug-in parameters in the Kubelet service startup parameters:... --network-plugin=cni --cni-conf-dir=/etc/cni/net.d \ # 此目录下的配置文件要符合CNI规范。 --cni-bin-dir=/opt/kubernetes/bin/cni ...There are several open source projects that support deployment to kubernetes in the form of a network plug-in, inc
different ports supported by Linux and enables many-to-many communications like switches.
Routing : The Linux system contains a complete routing feature that uses the routing table to determine where to send the IP layer when it processes the data to be sent or forwarded.
Docker Eco-Technology stackShows the location of the Docker network throughout the Docker ecosystem stack:
Docker Network implementation
single-Machine network mode : Bridge, Host, Container, None, here specif
' {"Peerurls": ["/HTTP// 192.168.73.172:2380"]} 'Start the ETCD container on the new node and notice the difference in the Red font sectionetcd03 -advertise-client-urls http://192.168.73.150:2379,http://192.168.73.150:4001-listen-client-urls Http://0.0.0.0:2379-initial-advertise-peer-urls Http://192.168.73.150:2380-listen-peer-urls http://0.0.0.0:2380- Initial-cluster-token Etcd-cluster-initial-cluster "etcd01=http://192.168.73.140:2380,etcd02=http:// 192.168.73.137:2380,etcd03=http://192.168.7
1. The Calico node container runs in the daemonset mode in kubernetes. The container network mode is hostnetwor. It shares the network stack with the host and has the same IP address and hostname.
2. view a pod: [email protected] ~] # Kubectl get pods-O wide-N Kube-system | grep-I Tiller
Tiller-deploy-5dfffddb8d-n4vp6 1/1 running 0 3D 10.233.122.4 bserver42
3. view the NIC and IP address of a pod
Use cali
Kubernetes can connect pods on different node nodes in the cluster, and by default, each pod is accessible to each other. However, in some scenarios, different pods should not be interoperable, and access control is required at this time. So how does it work?Brief introduction?? Kubernetes provides Networkpolicy feature, which supports network access control by namespace and by pod level. It uses the label
First of all, to everyone popular science under the kubernetes choice of the network interface, a brief introduction of the network implementation of the background.The container network Interface is a set of container networks definition specification, including method specification, parameter specification, response specification and so on. The MLM only requires that network resources be freed when the container is created, when the container is all
Failed to create Calico network using Docker.# docker network create --driver calico --ipam-driver calico-ipam testcalicoError response from daemon: failed to update store for object type *libnetwork.endpointCnt: client: response is invalid json. The endpoint is probably not valid etcd cluster endpoint.To view Docker logs:# Journalctl-fu Docker--Logs begin at Sun
NetworkingKubernetes supports for Third-party netwroking the cluster via the MLM plugin. For more infromation, please see Cluster Networking.According to this Chinese blog, Principles and Solutions of Kubernetes Networking from Yourongyun the three top of the MLM Pro Viders for kubernetes cluster based on VMs is Project Calico, flannel, Weave Net.And also, here
In the previous section we deployed the Calico network, and today we will run the container and analyze the Calico network structure.Run the container bbox1 in host1 and connect to Cal_net1:
Docker container run--net cal_net1--name bbox1-tid busybox
View the Bbox1 network configuration.
Cali0 is a calico interface, with an assigned IP of 192.168.119.2. Cali0 co
Reference Address: Https://github.com/gjmzj/kubeasz
IntroductionProvides tools for quickly deploying highly available k8s clusters, deploying in binary mode and automating with Ansible-playbook, providing a one-click installation script or stepping through the installation of individual components while explaining the main parameter configurations and considerations for each step.CharacteristicsCluster Features: TLS bidirectional authentication, RBAC authorization, multi-master high availab
This example is mainly to use ready-made flower patterns, using Photoshop magic wand to pull out the outline, and then with a dark blue background to make a blue calico effect. Everyone in the choice of flower pattern must pay attention to select some outline lines slightly thick and clear material pictures, so that the formation of flower patterns will be much easier. Otherwise it will be a test of your pull and hook chart level.
Let's take a look a
, no longer repeat it.Third, kubernetes integrated calicoCalico is a pure 3-tier data center network solution and seamlessly integrates with an IaaS cloud architecture like OpenStack to provide controlled IP communication between VMS, containers, and bare metal.By compressing the entire Internet's extensible IP Network principles to the data center level, Calico uses Linux kernel to implement an efficient v
Resources:k8s-Network Isolation Reference
Opencontrail is a open source network virtualization platform for the cloud. –kube-o-contrail–get your hands dirty with Kubernetes and Opencontrail
Opencontrail is a open source network virtualization platform for the cloud.
Opencontrail Architecture Document-flying Eagle's diary-NetEase Blog
Opencontrail Study (i)-wanjia19870902 's Colu
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.